|
1. Selecting the infrastructure
| In consultation with the future maintenance department of the infrastructure, an inventory is drawn up of which parts are
now actually used (the configuration) and what is ‘worth’ transferring. The decision should be made based on the
consideration of what it costs to keep and maintain the infrastructure, and what it would cost to realise the
infrastructure again at a later stage. Besides this, there is the possibility that certain software or hardware (such as
parts of the test environment, but also certain test tools) are only of use during the initial phase of the testing and are
no longer necessary. It is then a waste of effort taking this under maintenance. This identification can also clarify the
difference between the specified infrastructure and the infrastructure actually used. There can be discrepancies here
(certain software or hardware that was set up but never used) and this point of learning can be taken forward into the
evaluation of the test process (see the task Evaluate The Test Process (AST)). |
2. Collecting and refining the infrastructure
| The description of the infrastructure in the “Detailed specification of the infrastructure” should be adapted to the confi
guration that is to be transferred. This is of essential importance, as otherwise everything will have to be created anew
for future tests. It is important with this description to look carefully at the configuration of the workplaces. In this
“Detailed specification of the infrastructure” a list is included containing the components that are transferred.
Components may be licences, environment data, scripts, software, tools, registry files, hardware, accounts, databases,
files, et cetera. |
3. Transferring the infrastructure
| Finally, the actual transfer of the infrastructure takes place. The configuration is transferred according to the adapted
list in the document “Detailed specification of the infrastructure”. |
|
